Building a simple Fabric MCP server

I got tired of MCPs that proxy calls through another LLM when I'm already using the LLM I want to use. It drives me crazy: it creates unnecessary complexity, breaks conversation flow, and prevents real-time prompt modification.

So I built the Pattern MCP Server. Simple concept: expose prompt content directly instead of executing it through a middleman.

While building it, I went through Fabric's 215 patterns.

✅ A-tier (15%): Security patterns like analyze_malware are genuinely excellent

❌ D/F-tier (15%): find_female_life_partner reduces relationships to algorithms (icky)

The bigger issues I found:

• Cargo cult prompt engineering ("think with 1,419 IQ")
• Over-rigid constraints ("write exactly 16 words per bullet")
• 90% lack examples despite examples being the most powerful instructional tool
• Anxiety-driven repetition ("DO NOT COMPLAIN" x3)

Added notes on how to fix said issues.

Anyway: Everyone needs their prompt library. The best prompts are ones you've refined for your specific workflow.

The Pattern MCP Server gives you direct access to prompts (both Fabric's collection and your custom patterns) without execution overhead. Mix, match, and modify on the fly.